Release 1.2.0#2317
Closed
MarcusSorealheis wants to merge 2 commits into
Closed
Conversation
MarcusSorealheis
temporarily deployed
to
production
GitHub Actions
Inactive
MarcusSorealheis
temporarily deployed
to
production
GitHub Actions
Inactive
MarcusSorealheis
temporarily deployed
to
production
GitHub Actions
Inactive
MarcusSorealheis
temporarily deployed
to
production
GitHub Actions
Inactive
amankrx
reviewed
May 11, 2026
| @@ -3,6 +3,32 @@ | |||
|
|
|||
| All notable changes to this project will be documented in this file. | |||
Member
There was a problem hiding this comment.
There are changes here to the old version as well. That should be reverted.
Member
|
Duplicate of #2337 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
See the Changelog for the most comprehensive description.
One important matter to call out is the quick succession of breaking releases is not necessarily related to a flaw in the product for most customers. We introduced some scalability options that impact users running both CAS and Scheduler clusters, as opposed to single node deployments.
Type of change
Please delete options that aren't relevant.
not work as expected)
How Has This Been Tested?
bazel test //...Checklist
bazel test //...passes locallygit amendsee some docsThis change is